Systems and methods for a non-destructive testing ecosystem

ABSTRACT

A non-transitory computer readable medium may include executable instructions which, when executed by a processor, cause the processor to provide for a non-destructive testing (NDT) ecosystem. The NDT ecosystem includes a repository of digital content, and a store configured to sell the digital content to a customer, wherein the digital content is executable by a NDT device and wherein the digital content is created by a plurality of entities.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/747,429 entitled “SYSTEMS AND METHODS FOR A NON-DESTRUCTIVE TESTINGECOSYSTEM,” filed Jan. 22, 2013, which is incorporated by referenceherein in its entirety.

FIELD

The subject matter disclosed herein relates to non-destructive testing(NDT) systems, and particularly to systems and methods for a NDTecosystem.

BACKGROUND

Certain equipment and facilities, such as power generation equipment andfacilities, oil and gas equipment and facilities, aircraft equipment andfacilities, manufacturing equipment and facilities, and the like,include a plurality of interrelated systems, and processes. For example,power generation plants may include turbine systems and processes foroperating and maintaining the turbine systems. Likewise, oil and gasoperations may include carbonaceous fuel retrieval systems andprocessing equipment interconnected via pipelines. Similarly, aircraftsystems may include airplanes and maintenance hangars useful inmaintaining airworthiness and providing for maintenance support. Duringequipment operations, the equipment may degrade, encounter undesiredconditions such as corrosion, wear and tear, and so on, potentiallyaffecting overall equipment effectiveness. Certain inspectiontechniques, such as non-destructive inspection techniques ornon-destructive testing (NDT) techniques, may be used to detectundesired equipment conditions.

In a conventional NDT system, data may be shared with other NDToperators or personnel using portable memory devices, paper, of throughthe telephone. As such, the amount of time to share data between NDTpersonnel may depend largely on the speed at which the physical portablememory device is physically dispatched to its target. Accordingly, itwould be beneficial to improve the data sharing capabilities of the NDTsystem, for example, to more efficiently test and inspect a variety ofsystems and equipment.

BRIEF DESCRIPTION

Certain embodiments commensurate in scope with the originally claimedinvention are summarized below. These embodiments are not intended tolimit the scope of the claimed invention, but rather these embodimentsare intended only to provide a brief summary of possible forms of theinvention. Indeed, the invention may encompass a variety of forms thatmay be similar to or different from the embodiments set forth below.

In one embodiment, a non-transitory computer readable medium may includeexecutable instructions which, when executed by a processor, cause theprocessor to provide for a non-destructive testing (NDT) ecosystem. TheNDT ecosystem includes a repository of digital content, and a storeconfigured to sell the digital content to a customer, wherein thedigital content is executable by a NDT device and wherein the digitalcontent is created by a plurality of entities.

In another embodiment, a system may include a non-destructive testing(NDT) device configured to communicatively couple to an NDT ecosystem,wherein the NDT device is configured to download executable digitalcontent, non-executable digital content, or a combination thereof, froma digital store included in the NDT ecosystem.

In yet another embodiment, a method includes providing for anon-destructive testing (NDT) ecosystem. The NDT ecosystem includes arepository of digital content, and a store configured to sell thedigital content to a customer, wherein the digital content is executableby a NDT device and wherein the digital content is created by aplurality of entities.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features, aspects, and advantages of the presentinvention will become better understood when the following detaileddescription is read with reference to the accompanying drawings in whichlike characters represent like parts throughout the drawings, wherein:

FIG. 1 illustrates an embodiment of a power plant having annon-destructive testing (NDT) system, in accordance with aspects of thepresent disclosure;

FIG. 2 is a schematic diagram of an embodiment of the NDT system of FIG.1 , in accordance with aspects of the present disclosure;

FIG. 3 is a block diagram illustrating an embodiment of a system usefulin optimizing the power plant of FIG. 1 , in accordance with aspects ofthe present disclosure;

FIG. 4 is an illustration of an embodiment of a graphical user interfaceof the NDT system of FIG. 1 , in accordance with aspects of the presentdisclosure;

FIG. 5 is a flow chart illustrating an embodiment of a process useful inimproving performance of the power plant of FIG. 1 , in accordance withaspects of the present disclosure;

FIG. 6 is a block diagram of an embodiment of information flow through awireless conduit of information communicated by the NDT inspectionsystem of FIG. 1 ;

FIG. 7 is a block diagram of an embodiment of information flow through awireless conduit of information useful in remote control of the NDTinspection system of FIG. 1 ;

FIG. 8 is a block diagram of an embodiment of an NDT ecosystem;

FIG. 9 is an illustration of embodiments of digital content managed bythe NDT ecosystem of FIG. 8 ;

FIG. 10 is a flowchart of an embodiment of a process for using the NDTecosystem of FIG. 8 to purchase NDT items;

FIG. 11 is a flowchart of an embodiment of a process for using the NDTecosystem of FIG. 8 to add or remove licenses;

FIG. 12 a flowchart of an embodiment of a process for using the NDTecosystem of FIG. 8 to synchronize NDT inspection devices; and

FIG. 13 a flowchart of an embodiment of a process for using the NDTecosystem of FIG. 8 to manage NDT inspection devices.

DETAILED DESCRIPTION

One or more specific embodiments will be described below. In an effortto provide a concise description of these embodiments, not all featuresof an actual implementation are described in the specification. Itshould be appreciated that in the development of any such actualimplementation, as in any engineering or design project, numerousimplementation-specific decisions must be made to achieve thedevelopers' specific goals, such as compliance with system-related andbusiness-related constraints, which may vary from one implementation toanother. Moreover, it should be appreciated that such a developmenteffort might be complex and time consuming, but would nevertheless be aroutine undertaking of design, fabrication, and manufacture for those ofordinary skill having the benefit of this disclosure.

When introducing elements of various embodiments of the presentinvention, the articles “a,” “an,” “the,” and “said” are intended tomean that there are one or more of the elements. The terms “comprising,”“including,” and “having” are intended to be inclusive and mean thatthere may be additional elements other than the listed elements.

Embodiments of the present disclosure may apply to a variety ofinspection and testing techniques, including non-destructive testing(NDT) or inspection systems. In the NDT system, certain techniques suchas borescopic inspection, weld inspection, remote visual inspections,x-ray inspection, ultrasonic inspection, eddy current inspection, andthe like, may be used to analyze and detect a variety of conditions,including but not limited to corrosion, equipment wear and tear,cracking, leaks, and so on. The techniques described herein provide forimproved NDT systems suitable for borescopic inspection, remote visualinspections, x-ray inspection, ultrasonic inspection, and/or eddycurrent inspection, enabling enhanced data gathering, data analysis,inspection/testing processes, and NDT collaboration techniques.

The improved NDT systems described herein may include inspectionequipment using wireless conduits suitable for communicatively couplingthe inspection equipment to mobile devices, such as tablets, smartphones, and augmented reality eyeglasses; to computing devices, such asnotebooks, laptops, workstations, personal computers; and to “cloud”computing systems, such as cloud-based NDT ecosystems, cloud analytics,cloud-based collaboration and workflow systems, distributed computingsystems, expert systems and/or knowledge-based systems. Indeed, thetechniques described herein may provide for enhanced NDT data gathering,analysis, and data distribution, thus improving the detection ofundesired conditions, enhancing maintenance activities, and increasingreturns on investment (ROI) of facilities and equipment.

In one embodiment, a tablet may be communicatively coupled to the NDTinspection device (e.g., borescope, transportable pan-tilt-zoom camera,eddy current device, x-ray inspection device, ultrasonic inspectiondevice), such as a MENTOR™ NDT inspection device, available from GeneralElectric, Co., of Schenectady, N.Y., and used to provide, for example,enhanced wireless display capabilities, remote control, data analyticsand/or data communications to the NDT inspection device. While othermobile devices may be used, the use of the tablet is apt, however,insofar as the tablet may provide for a larger, higher resolutiondisplay, more powerful processing cores, an increased memory, andimproved battery life. Accordingly, the tablet may address certainissues, such as providing for improved visualization of data, improvingthe manipulatory control of the inspection device, and extendingcollaborative sharing to a plurality of external systems and entities.

Keeping the foregoing in mind, the present disclosure is directedtowards sharing data acquired from the NDT system and/or control ofapplications and/or devices in the NDT system. Generally, data generatedfrom the NDT system may be automatically distributed to various peopleor groups of people using techniques disclosed herein. Moreover, contentdisplayed by an application used to monitor and/or control devices inthe NDT system may be shared between individuals to create a virtualcollaborative environment for monitoring and controlling the devices inthe NDT system.

By way of introduction, and turning now to FIG. 1 , the figure is ablock diagram of an embodiment of distributed NDT system 10. In thedepicted embodiment, the distributed NDT system 10 may include one ormore NDT inspection devices 12. The NDT inspection devices 12 may bedivided into at least two categories. In one category, depicted in FIG.1 , the NDT inspection devices 12 may include devices suitable forvisually inspecting a variety of equipment and environments. In anothercategory, described in more detail with respect to FIG. 2 below, the NDTdevices 12 may include devices providing for alternatives to visualinspection modalities, such as x-ray inspection modalities, eddy currentinspection modalities, and/or ultrasonic inspection modalities.

In the depicted first example category of FIG. 1 , the NDT inspectiondevices 12 may include a borescope 14 having one or more processors 15and a memory 17, and a transportable pan-tilt-zoom (PTZ) camera 16having one or more processors 19 and a memory 21. In this first categoryof visual inspection devices, the bore scope 14 and PTZ camera 16 may beused to inspect, for example, a turbo machinery 18, and a facility orsite 20. As illustrated, the bore scope 14 and the PTZ camera 16 may becommunicatively coupled to a mobile device 22 also having one or moreprocessors 23 and a memory 25. The mobile device 22 may include, forexample, a tablet, a cell phone (e.g., smart phone), a notebook, alaptop, or any other mobile computing device. The use of a tablet,however, is apt insofar as the tablet provides for a good balancebetween screen size, weight, computing power, and battery life.Accordingly, in one embodiment, the mobile device 22 may be the MENTOR™tablet mentioned above, available from General Electric Co., ofSchenectady, N.Y., and providing for touchscreen input. The mobiledevice 22 may be communicatively coupled to the NDT inspection devices12, such as the bore scope 14 and/or the PTZ camera 16, through avariety of wireless or wired conduits. For example, the wirelessconduits may include WiFi (e.g., Institute of Electrical and ElectronicsEngineers [IEEE] 802.11X), cellular conduits (e.g., high speed packetaccess [HSPA], HSPA+, long term evolution [LTE], WiMax), near fieldcommunications (NFC), Bluetooth, personal area networks (PANs), and thelike. The wireless conduits may use a variety of communicationprotocols, such as TCP/IP, UDP, SCTP, socket layers, and so on. Incertain embodiments, the wireless or wired conduits may include securelayers, such as secure socket layers (SSL), virtual private network(VPN) layers, encrypted layers, challenge key authentication layers,token authentication layers, and so on. Wired conduits may includeproprietary cabling, RJ45 cabling, co-axial cables, fiber optic cables,and so on.

Additionally or alternatively, the mobile device 22 may becommunicatively coupled to the NDT inspection devices 12, such as theborescope 14 and/or the PTZ camera 16, through the “cloud” 24. Indeed,the mobile device 22 may use the cloud 24 computing and communicationstechniques (e.g., cloud-computing network), including but not limited toHTTP, HTTPS, TCP/IP, service oriented architecture (SOA) protocols(e.g., simple object access protocol [SOAP], web services descriptionlanguages (WSDLs)) to interface with the NDT inspection devices 12 fromany geographic location, including geographic locations remote from thephysical location about to undergo inspection. Further, in oneembodiment, the mobile device 22 may provide “hot spot” functionality inwhich mobile device 22 may provide wireless access point (WAP)functionality suitable for connecting the NDT inspection devices 12 toother systems in the cloud 24. Accordingly, collaboration may beenhanced by providing for multi-party workflows, data gathering, anddata analysis.

For example, a borescope operator 26 may physically manipulate theborescope 14 at one location, while a mobile device operator 28 may usethe mobile device 22 to interface with and physically manipulate thebore scope 14 at a second location through remote control techniques.The second location may be proximate to the first location, orgeographically distant from the first location. Likewise, a cameraoperator 30 may physically operate the PTZ camera 16 at a thirdlocation, and the mobile device operator 28 may remote control PTZcamera 16 at a fourth location by using the mobile device 22. The fourthlocation may be proximate to the third location, or geographicallydistant from the third location. Any and all control actions performedby the operators 26 and 30 may be additionally performed by the operator28 through the mobile device 22. Additionally, the operator 28 maycommunicate with the operators 26 and/or 30 by using the devices 14, 16,and 22 through techniques such as voice over IP (VOIP), virtualwhiteboarding, text messages, and the like. By providing for remotecollaboration techniques between the operator 28 operator 26, andoperator 30, the techniques described herein may provide for enhancedworkflows and increase resource efficiencies. Indeed, nondestructivetesting processes may leverage the communicative coupling of the cloud24 with the mobile device 22, the NDT inspection devices 12, andexternal systems coupled to the cloud 24.

In one mode of operation, the mobile device 22 may be operated by thebore scope operator 26 and/or the camera operator 30 to leverage, forexample, a larger screen display, more powerful data processing, as wellas a variety of interface techniques provided by the mobile device 22,as described in more detail below. Indeed, the mobile device 22 may beoperated alongside or in tandem with the devices 14 and 16 by therespective operators 26 and 30. This enhanced flexibility provides forbetter utilization of resources, including human resources, and improvedinspection results.

Whether controlled by the operator 28, 26, and/or 30, the borescope 14and/or PTZ camera 16 may be used to visually inspect a wide variety ofequipment and facilities. For example, the bore scope 14 may be insertedinto a plurality of borescope ports and other locations of theturbomachinery 18, to provide for illumination and visual observationsof a number of components of the turbomachinery 18. In the depictedembodiment, the turbo machinery 18 is illustrated as a gas turbinesuitable for converting carbonaceous fuel into mechanical power.However, other equipment types may be inspected, including compressors,pumps, turbo expanders, wind turbines, hydroturbines, industrialequipment, and/or residential equipment. The turbomachinery 18 (e.g.,gas turbine) may include a variety of components that may be inspectedby the NDT inspection devices 12 described herein.

With the foregoing in mind, it may be beneficial to discuss certainturbomachinery 18 components that may be inspected by using theembodiments disclosed herein. For example, certain components of theturbomachinery 18 depicted in FIG. 1 , may be inspected for corrosion,erosion, cracking, leaks, weld inspection, and so on. Mechanicalsystems, such as the turbomachinery 18, experience mechanical andthermal stresses during operating conditions, which may require periodicinspection of certain components. During operations of theturbomachinery 18, a fuel such as natural gas or syngas, may be routedto the turbomachinery 18 through one or more fuel nozzles 32 into acombustor 36. Air may enter the turbomachinery 18 through an air intakesection 38 and may be compressed by a compressor 34. The compressor 34may include a series of stages 40, 42, and 44 that compress the air.Each stage may include one or more sets of stationary vanes 46 andblades 48 that rotate to progressively increase the pressure to providecompressed air. The blades 48 may be attached to rotating wheels 50connected to a shaft 52. The compressed discharge air from thecompressor 34 may exit the compressor 34 through a diffuser section 56and may be directed into the combustor 36 to mix with the fuel. Forexample, the fuel nozzles 32 may inject a fuel-air mixture into thecombustor 36 in a suitable ratio for optimal combustion, emissions, fuelconsumption, and power output. In certain embodiments, theturbomachinery 18 may include multiple combustors 36 disposed in anannular arrangement. Each combustor 36 may direct hot combustion gasesinto a turbine 54.

As depicted, the turbine 54 includes three separate stages 60, 62, and64 surrounded by a casing 76. Each stage 60, 62, and 64 includes a setof blades or buckets 66 coupled to a respective rotor wheel 68, 70, and72, which are attached to a shaft 74. As the hot combustion gases causerotation of turbine blades 66, the shaft 74 rotates to drive thecompressor 34 and any other suitable load, such as an electricalgenerator. Eventually, the turbomachinery 18 diffuses and exhausts thecombustion gases through an exhaust section 80. Turbine components, suchas the nozzles 32, intake 38, compressor 34, vanes 46, blades 48, wheels50, shaft 52, diffuser 56, stages 60, 62, and 64, blades 66, shaft 74,casing 76, and exhaust 80, may use the disclosed embodiments, such asthe NDT inspection devices 12, to inspect and maintain said components.

Additionally, or alternatively, the PTZ camera 16 may be disposed atvarious locations around or inside of the turbo machinery 18, and usedto procure visual observations of these locations. The PTZ camera 16 mayadditionally include one or more lights suitable for illuminatingdesired locations, and may further include zoom, pan and tilt techniquesdescribed in more detail below with respect to FIG. 4 , useful forderiving observations around in a variety of difficult to reach areas.The borescope 14 and/or the camera 16 may be additionally used toinspect the facilities 20, such as an oil and gas facility 20. Variousequipment such as oil and gas equipment 84, may be inspected visually byusing the borescope 14 and/or the PTZ camera 16. Advantageously,locations such as the interior of pipes or conduits 86, underwater (orunderfluid) locations 88, and difficult to observe locations such aslocations having curves or bends 90, may be visually inspected by usingthe mobile device 22 through the borescope 14 and/or PTZ camera 16.Accordingly, the mobile device operator 28 may more safely andefficiently inspect the equipment 18, 84 and locations 86, 88, and 90,and share observations in real-time or near real-time with locationgeographically distant from the inspection areas. It is to be understoodthat other NDT inspection devices 12 may be use the embodimentsdescribed herein, such as fiberscopes (e.g., articulating fiberscope,non-articulating fiberscope), and remotely operated vehicles (ROVs),including robotic pipe inspectors and robotic crawlers.

Turning now to FIG. 2 , the figure is a block diagram of an embodimentof the distributed NDT system 10 depicting the second category of NDTinspection devices 12 that may be able to provide for alternativeinspection data to visual inspection data. For example, the secondcategory of NDT inspection devices 12 may include an eddy currentinspection device 92, an ultrasonic inspection device, such as anultrasonic flaw detector 94, and an x-ray inspection device, such adigital radiography device 96. The eddy current inspection device 92 mayinclude one or more processors 93 and a memory 95. Likewise, theultrasonic flaw detector 94 may include one or more processors 97 and amemory 104. Similarly, the digital radiography device 96 may include oneor more processors 101 and a memory 103. In operations, the eddy currentinspection device 92 may be operated by an eddy current operator 98, theultrasonic flaw detector 94 may be operated by an ultrasonic deviceoperator 100, and the digital radiography device 96 may be operated by aradiography operator 102.

As depicted, the eddy current inspection device 92, the ultrasonic flawdetector 94, and the digital radiography inspection device 96, may becommunicatively coupled to the mobile device 22 by using wired orwireless conduits, including the conduits mentioned above with respectto FIG. 1 . Additionally, or alternatively, the devices 92, 94, and 96may be coupled to the mobile device 22 by using the cloud 24, forexample the borescope 14 may be connected to a cellular “hotspot,” anduse the hotspot to connect to one or more experts in borescopicinspection and analysis. Accordingly, the mobile device operator 28 mayremotely control various aspects of operations of the devices 92, 94,and 96 by using the mobile device 22, and may collaborate with theoperators 98, 100, and 102 through voice (e.g., voice over IP [VOIP]),data sharing (e.g., whiteboarding), providing data analytics, expertsupport and the like, as described in more detail herein.

Accordingly, it may be possible to enhance the visual observation ofvarious equipment, such as an aircraft system 104 and facilities 106,with x-ray observation modalities, ultrasonic observation modalities,and/or eddy current observation modalities. For example, the interiorand the walls of pipes 108 may be inspected for corrosion and/orerosion. Likewise, obstructions or undesired growth inside of the pipes108 may be detected by using the devices 92, 94, and/or 96. Similarly,fissures or cracks 110 disposed inside of certain ferrous or non-ferrousmaterial 112 may be observed. Additionally, the disposition andviability of parts 114 inserted inside of a component 116 may beverified. Indeed, by using the techniques described herein, improvedinspection of equipment and components 104, 108, 112 and 116 may beprovided. For example, the mobile device 22 may be used to interfacewith and provide remote control of the devices 14, 16, 92, 94, and 96.

FIG. 3 is a front view of the borescope 14 coupled to the mobile device22 and the cloud 24. Accordingly, the boresecope 14 may provide data toany number of devices connected to the cloud 24 or inside the cloud 24.As mentioned above, the mobile device 22 may be used to receive datafrom the borescope 14, to remote control the borescope 14, or acombination thereof. Indeed, the techniques described herein enable, forexample, the communication of a variety of data from the borescope 14 tothe mobile device 22, including but not limited to images, video, andsensor measurements, such as temperature, pressure, flow, clearance(e.g., measurement between a stationary component and a rotarycomponent), and distance measurements. Likewise, the mobile device 22may communicate control instructions, reprogramming instructions,configuration instructions, and the like, as described in more detailbelow.

As depicted the borescope 14, includes an insertion tube 118 suitablefor insertion into a variety of location, such as inside of theturbomachinery 18, equipment 84, pipes or conduits 86, underwaterlocations 88, curves or bends 90, varies locations inside or outside ofthe aircraft system 104, the interior of pipe 108, and so on. Theinsertion tube 118 may include a head end section 120, an articulatingsection 122, and a conduit section 124. In the depicted embodiment, thehead end section 120 may include a camera 126, one or more lights 128(e.g., LEDs), and sensors 130. As mentioned above, the borescope'scamera 126 may provide images and video suitable for inspection. Thelights 128 may be used to provide for illumination when the head end 120is disposed in locations having low light or no light.

During use, the articulating section 122 may be controlled, for example,by the mobile device 22 and/or a physical joy stick 131 disposed on theborescope 14. The articulating sections 122 may steer or “bend” invarious dimensions. For example, the articulation section 122 may enablemovement of the head end 120 in an X-Y plane X-Z plane and/or Y-Z planeof the depicted XYZ axes 133. Indeed, the physical joystick 131 and/orthe mobile device 22 may both be used alone or in combination, toprovide control actions suitable for disposing the head end 120 at avariety of angles, such as the depicted angle α. In this manner, theborescope head end 120 may be positioned to visually inspect desiredlocations. The camera 126 may then capture, for example, a video 134,which may be displayed in a screen 135 of the borescope 14 and a screen137 of the mobile device 22, and may be recorded by the borescope 14and/or the mobile device 22. In one embodiment, the screens 135 and 137may be multi-touchscreens using capacitance techniques, resistivetechniques, infrared grid techniques, and the like, to detect the touchof a stylus and/or one or more human fingers. Additionally oralternatively, images and the video 134 may be transmitted into thecloud 24.

Other data, including but not limited to sensor 130 data, mayadditionally be communicated and/or recorded by the borescope 14. Thesensor 130 data may include temperature data, distance data, clearancedata (e.g., distance between a rotating and a stationary component),flow data, and so on. In certain embodiments, the borescope 14 mayinclude a plurality of replacement tips 136. For example, thereplacement tips 136 may include retrieval tips such as snares, magnetictips, gripper tips, and the like. The replacement tips 136 mayadditionally include cleaning and obstruction removal tools, such aswire brushes, wire cutters, and the like. The tips 136 may additionallyinclude tips having differing optical characteristics, such as focallength, stereoscopic views, 3-dimensional (3D) phase views, shadowviews, and so on. Additionally or alternatively, the head end 120 mayinclude a removable and replaceable head end 120. Accordingly, aplurality of head ends 120 may be provided at a variety of diameters,and the insertion tube 118 maybe disposed in a number of locationshaving openings from approximately one millimeter to ten millimeters ormore. Indeed, a wide variety of equipment and facilities may beinspected, and the data may be shared through the mobile device 22and/or the cloud 24.

FIG. 4 is a perspective view of an embodiment of the transportable PTZcamera 16 communicatively coupled to the mobile device 22 and to thecloud 24. As mentioned above, the mobile device 22 and/or the cloud 24may remotely manipulate the PTZ camera 16 to position the PTZ camera 16to view desired equipment and locations. In the depicted example, thePTZ camera 16 may be tilted and rotated about the Y-axis. For example,the PTZ camera 16 may be rotated at an angle β between approximately 0°to 180°, 0° to 270°, 0° to 360°, or more about the Y-axis. Likewise, thePTZ camera 16 may be tilted, for example, about the Y-X plane at anangle γ of approximately 0° to 100°, 0° to 120°, 0° to 150°, or morewith respect to the Y-Axis. Lights 138 may be similarly controlled, forexample, to active or deactivate, and to increase or decrease a level ofillumination (e.g., lux) to a desired value. Sensors 140, such as alaser rangefinder, may also be mounted onto the PTZ camera 16, suitablefor measuring distance to certain objects. Other sensors 140 may beused, including long-range temperature sensors (e.g., infraredtemperature sensors), pressure sensors, flow sensors, clearance sensors,and so on.

The PTZ camera 16 may be transported to a desired location, for example,by using a shaft 142. The shaft 142 enables the camera operator 30 tomove the camera and to position the camera, for example, inside oflocations 86, 108, underwater 88, into hazardous (e.g., hazmat)locations, and so on. Additionally, the shaft 142 may be used to morepermanently secure the PTZ camera 16 by mounting the shaft 142 onto apermanent or semi-permanent mount. In this manner, the PTZ camera 16 maybe transported and/or secured at a desired location. The PTZ camera 16may then transmit, for example by using wireless techniques, image data,video data, sensor 140 data, and the like, to the mobile device 22and/or cloud 24. Accordingly, data received from the PTZ camera 16 maybe remotely analyzed and used to determine the condition and suitabilityof operations for desired equipment and facilities. Indeed, thetechniques described herein may provide for a comprehensive inspectionand maintenance process suitable for planning, inspecting, analyzing,and/or sharing a variety of data by using the aforementioned devices 12,14, 16, 22, 92, 94, 96, and the cloud 24, as described in more detailbelow with respect to FIG. 5 .

FIG. 5 is a flowchart of an embodiment of a process 150 suitable forplanning, inspecting, analyzing, and/or sharing a variety of data byusing the aforementioned devices 12, 14, 16, 22, 92, 94, 96, and thecloud 24. Indeed, the techniques described herein may use the devices12, 14, 16, 22, 92, 94, 96 to enable processes, such as the depictedprocess 150, to more efficiently support and maintain a variety ofequipment. In certain embodiments, the process 150 or portions of theprocess 150 may be included in non-transitory computer-readable mediastored in memory, such as the memory 15, 19, 23, 93, 97, 101 andexecutable by one or more processors, such as the processors 17, 21, 25,95, 99, 103.

In one example, the process 150 may plan (block 152) for inspection andmaintenance activities. Data acquired by using the devices 12, 14, 16,22, 42, 44, 46, an others, such as fleet data acquired from a fleet ofturbomachinery 18, from equipment users (e.g., aircraft 104 servicecompanies), and/or equipment manufacturers, may be used to plan (block152) maintenance and inspection activities, more efficient inspectionschedules for machinery, flag certain areas for a more detailedinspection, and so on. The process 150 may then enable the use of asingle mode or a multi-modal inspection (block 154) of desiredfacilities and equipment (e.g., turbomachinery 18). As mentioned above,the inspection (block 154) may use any one or more of the NDT inspectiondevices 12 (e.g., borescope 14, PTZ camera 16, eddy current inspectiondevice 92, ultrasonic flaw detector 94, digital radiography device 96),thus providing with one or more modes of inspection (e.g., visual,ultrasonic, eddy current, x-ray). In the depicted embodiment, the mobiledevice 22 may be used to remote control the NDT inspection devices 12,to analyze data communicated by the NDT inspection devices 12, toprovide for additional functionality not included in the NDT inspectiondevices 12 as described in more detail herein, to record data from theNDT inspection devices 12, and to guide the inspection (block 154), forexample, by using menu-driven inspection (MDI) techniques, among others.

Results of the inspection (block 154), may then be analyzed (block 156),for example, by using the NDT device 12, by transmitting inspection datato the cloud 24, by using the mobile device 22, or a combinationthereof. The analysis may include engineering analysis useful indetermining remaining life for the facilities and/or equipment, wear andtear, corrosion, erosion, and so forth. The analysis may additionallyinclude operations research (OR) analysis used to provide for moreefficient parts replacement schedules, maintenance schedules, equipmentutilization schedules, personnel usage schedules, new inspectionschedules, and so on. The analysis (block 156) may then be reported(block 158), resulting in one or more reports 159, including reportscreated in or by using the cloud 24, detailing the inspection andanalysis performed and results obtained. The reports 159 may then beshared (block 160), for example, by using the cloud 24, the mobiledevice 22, and other techniques, such as workflow sharing techniques. Inone embodiment, the process 150 may be iterative, thus, the process 150may iterate back to planning (block 152) after the sharing (block 160)of the reports 159. By providing for embodiments useful in using thedevices (e.g., 12, 14, 16, 22, 92, 94, 96) described herein to plan,inspect, analyze, report, and share data, the techniques describedherein may enable a more efficient inspection and maintenance of thefacilities 20, 106 and the equipment 18, 104. Indeed, the transfer ofmultiple categories of data may be provided, as described in more detailbelow with respect to FIG. 6 .

FIG. 6 is a data flow diagram depicting an embodiment of the flow ofvarious data categories originating from the NDT inspection devices 12(e.g., devices 14, 16, 92, 94, 96) and transmitted to the mobile device22 and/or the cloud 24. As mentioned above, the NDT inspection devices12 may use a wireless conduit 162 to transmit the data. In oneembodiment, the wireless conduit 112 may include WiFi (e.g., 802.11X),cellular conduits (e.g., HSPA, HSPA+, LTE, WiMax), NFC, Bluetooth, PANs,and the like. The wireless conduit 162 may use a variety ofcommunication protocols, such as TCP/IP, UDP, SCTP, socket layers, andso on. In certain embodiments, the wireless conduit 162 may includesecure layers, such as SSL, VPN layers, encrypted layers, challenge keyauthentication layers, token authentication layers, and so on.Accordingly, an authorization data 164 may be used to provide any numberof authorization or login information suitable to pair or otherwiseauthenticate the NDT inspection device 12 to the mobile device 22 and/orthe cloud 24. Additionally, the wireless conduit 162 may dynamicallycompress data, depending on, for example, currently available bandwidthand latency. The mobile device 22 may then uncompress and display thedata. Compression/decompression techniques may include H.261, H.263,H.264, moving picture experts group (MPEG), MPEG-1, MPEG-2, MPEG-3,MPEG-4, DivX, and so on.

In certain modalities (e.g., visual modalities), images and video may becommunicated by using certain of the NDT inspection devices 12. Othermodalities may also send video, sensor data, and so on, related to orincluded in their respective screens. The NDT inspection device 12 may,in addition to capturing images, overlay certain data onto the image,resulting in a more informative view. For example, a borescope tip mapmay be overlaid on the video, showing an approximation of thedisposition of a borescope tip during insertion so as to guide theoperator 26 to more accurately position the borescope camera 126. Theoverlay tip map may include a grid having four quadrants, and the tip136 disposition may be displayed as dot in any portion or positioninside of the four quadrants. A variety of overlays may be provided, asdescribed in more detail below, including measurement overlays, menuoverlays, annotation overlays, and object identification overlays. Theimage and video data, such as the video 84, may then be displayed, withthe overlays generally displayed on top of the image and video data.

In one embodiment, the overlays, image, and video data may be “screenscraped” from the screen 135 and communicated as screen scrapping data166. The screen scrapping data 166 may then be displayed on the mobiledevice 22 and other display devices communicatively coupled to the cloud24. Advantageously, the screen scrapping data 166 may be more easilydisplayed. Indeed, because pixels may include both the image or videoand overlays in the same frame, the mobile device 22 may simply displaythe aforementioned pixels. However, providing the screen scraping datamay merge both the images with the overlays, and it may be beneficial toseparate the two (or more) data streams. For example, the separate datastreams (e.g., image or video stream, overlay stream) may be transmittedapproximately simultaneously, thus providing for faster datacommunications. Additionally, the data streams may be analyzedseparately, thus improving data inspection and analysis.

Accordingly, in one embodiment, the image data and overlays may beseparated into two or more data streams 168 and 170. The data stream 168may include only overlays, while the data stream 170 may include imagesor video. In one embodiment, the images or video 170 may be synchronizedwith the overlays 168 by using a synchronization signal 172. Forexample, the synchronization signal may include timing data suitable tomatch a frame of the data stream 170 with one or more data itemsincluded in the overlay stream 168. In yet another embodiment, nosynchronization data 172 data may be used. Instead, each frame or image170 may include a unique ID, and this unique ID may be matched to one ormore of the overlay data 168 and used to display the overlay data 168and the image data 170 together.

The overlay data 168 may include a tip map overlay. For example, a gridhaving four squares (e.g., quadrant grid) may be displayed, along with adot or circle representing a tip 136 position. This tip map may thusrepresent how the tip 136 is being inserted inside of an object. A firstquadrant (top right) may represent the tip 136 being inserted into a topright corner looking down axially into the object, a second quadrant(top left) may represent the tip 136 being inserted into a left rightcorner looking down axially, a third quadrant (bottom left) mayrepresent the tip 136 being inserted into a bottom left corner, and afourth quadrant (bottom right) may represent the tip 136 being insertedinto a bottom right corner. Accordingly, the borescope operator 26 maymore easily guide insertion of the tip 136.

The overlay data 168 may also include measurement overlays. For example,measurement such as length, point to line, depth, area, multi-segmentline, distance, skew, and circle gauge may be provided by enabling theuser to overlay one or more cursor crosses (e.g., “+”) on top of animage. In one embodiment a stereo probe measurement tip 136, or a shadowprobe measurement tip 136 may be provided, suitable for measurementsinside of objects, including stereoscopic measurements and/or byprojecting a shadow onto an object. By placing a plurality of cursoricons (e.g., cursor crosses) over an image, the measurements may bederived using stereoscopic techniques. For example, placing two cursorsicons may provide for a linear point-to-point measurement (e.g.,length). Placing three cursor icons may provide for a perpendiculardistance from a point to a line (e.g., point to line). Placing fourcursor icons may provide for a perpendicular distance between a surface(derived by using three cursors) and a point (the fourth cursor) aboveor below the surface (e.g., depth). Placing three or more cursors arounda feature or defect may then give an approximate area of the surfacecontained inside the cursors. Placing three or more cursors may alsoenable a length of a multi-segment line following each cursor.

Likewise, by projecting a shadow, the measurements may be derived basedon illumination and resulting shadows. Accordingly, by positioning theshadow across the measurement area, then placing two cursors as close aspossible to the shadow at furthermost points of a desired measurementmay result in the derivation of the distance between the points. Placingthe shadow across the measurement area, and then placing cursors atedges (e.g., illuminated edges) of the desired measurement areaapproximately to the center of a horizontal shadow may result in a skewmeasurement, otherwise defined as a linear (point-to-point) measurementon a surface that is not perpendicular to the probe 14 view. This may beuseful when a vertical shadow is not obtainable.

Similarly, positioning a shadow across the measurement area, and thenplacing one cursor on a raised surface and a second cursor on a recessedsurface may result in the derivation of depth, or a distance between asurface and a point above or below the surface. Positioning the shadownear the measurement area, and then placing a circle (e.g., circlecursor of user selectable diameter, also referred to as circle gauge)close to the shadow and over a defect may then derive the approximatediameter, circumference, and/or area of the defect.

Overlay data 168 may also include annotation data. For example, text andgraphics (e.g. arrow pointers, crosses, geometric shapes) may beoverlaid on top of an image to annotate certain features, such as“surface crack.” Additionally, audio may be captured by the NDTinspection device 12, and provided as an audio overlay. For example, avoice annotation, sounds of the equipment undergoing inspection, and soon, may be overlaid on an image or video as audio. The overlay data 168received by the mobile device 22 and/or cloud 24 may then be rendered bya variety of techniques. For example, HTML5 or other markup languagesmay be used to display the overlay data 168. In one embodiment, themobile device 22 and/or cloud 24 may provide for a first user interfacedifferent from a second user interface provided by the NDT device 12.Accordingly, the overlay data 168 may be simplified and only send basicinformation. For example, in the case of the tip map, the overlay data168 may simply include X and Y data correlative to the location of thetip, and the first user interface may then use the X and Y data tovisually display the tip on a grid.

Additionally sensor data 174 may be communicated. For example, data fromthe sensors 126, 140, and x-ray sensor data, eddy current sensor data,and the like may be communicated. In certain embodiments, the sensordata 174 may be synchronized with the overlay data 168, for example,overlay tip maps may be displayed alongside with temperatureinformation, pressure information, flow information, clearance, and soon. Likewise, the sensor data 174 may be displayed alongside the imageor video data 170.

In certain embodiments, force feedback or haptic feedback data 176 maybe communicated. The force feedback data 176 may include, for example,data related to the borescope 14 tip 136 abutting or contacting againsta structure, vibrations felt by the tip 136 or vibration sensors 126,force related to flows, temperatures, clearances, pressures, and thelike. The mobile device 22 may include, for example, a tactile layerhaving fluid-filled microchannels, which, based on the force feedbackdata 176, may alter fluid pressure and/or redirect fluid in response.Indeed, the techniques describe herein, may provide for responsesactuated by the mobile device 22 suitable for representing sensor data174 and other data in the conduit 162 as tactile forces.

The NDT devices 12 may additionally communicate position data 178. Forexample, the position data 178 may include locations of the NDT devices12 in relation to equipment 18, 104, and/or facilities 20, 106. Forexample, techniques such as indoor GPS, RFID, triangulation (e.g., WiFitriangulation, radio triangulation) may be used to determine theposition 178 of the devices 12. Object data 180 may include data relatedto the object under inspection. For example, the object data 180 mayinclude identifying information (e.g., serial numbers), observations onequipment condition, annotations (textual annotations, voiceannotations), and so on. Other types of data 182 may be used, includingbut not limited to menu-driven inspection data, which when used,provides a set of pre-defined “tags” that can be applied as textannotations and metadata. These tags may include location information(e.g., 1^(st) stage HP compressor) or indications (e.g., foreign objectdamage) related to the object undergoing inspection. Other data 182 mayadditionally include remote file system data, in which the mobile device22 may view and manipulate files and file constructs (e.g., folders,subfolders) of data located in the memory 25 of the NDT inspectiondevice 12. Accordingly, files may be transferred to the mobile device 22and cloud 24, edited and transferred back into the memory 25. Bycommunicating the data 164-182 to the mobile device 22 and the cloud 24,the techniques described herein may enable a faster and more efficientprocess 150. By communicating the data 164-182 to the mobile device 22and the cloud 24, the techniques described herein may enable a fasterand more efficient process 150. Indeed, the transfer of multiplecategories of data may be provided, as described in more detail belowwith respect to FIGS. 7-10 .

Turning now to FIG. 7 , the figure is a data flow diagram illustratingan embodiment of the flow of various data categories originating fromthe mobile device 22, devices inside the cloud 24, and/or devicescommunicatively connected to the cloud 24 (e.g., computing system 29)and directed, for example, towards the NDT inspection devices 12 (e.g.,borescope 14, PTZ camera 16, eddy current inspection device 92,ultrasonic flaw detector 94, digital radiography device 96). Such datamay include control data suitable for controlling the NDT device. Asdescribed herein, the control of the NDT inspection devices 12 includesboth control of positioning apparatus, such as the articulating section122 of the borescope 14, apparatus used to pan, tilt, and zoom the PTZcamera 16, as well as the remote control of file systems in the NDTdevices 12, screen(s) included in the NDT devices 12, and the setting ofparameters used to operate or to configure the NDT devices 12, asdescribed in more detail below.

In the depicted embodiment, a wireless conduit 200 may be used tocommunicate the data (e.g. control data) to the NDT devices 12. Similarto the conduit 162, the wireless conduit, in certain embodiments, mayinclude WiFi (e.g., 802.11X), cellular conduits (e.g., HSPA, HSPA+, LTE,WiMax), NFC, Bluetooth, PANs, and the like. The wireless conduit 162 mayuse a variety of communication protocols, such as TCP/IP, UDP, SCTP,socket layers, and so on. In certain embodiments, the wireless conduit162 may include secure layers, such as SSL, VPN layers, encryptedlayers, challenge key authentication layers, token authenticationlayers, and so on. It is to be noted that, in other embodiments, wiredconduits may be used alternative to or in lieu of the wireless conduits162, 200.

Authorization data 202 may be communicated, and used, for example, inconjunction with the authorization data 164 to enable secure access tothe NDT devices 12. A variety of secure authentication techniques may beused, including but not limited to login/password combinations,maintaining a list of secure MAC addresses, challenge-responseauthentication between two or more of the devices 12, 22, and cloud 24,secure NFC authentication, using a third-party authentication server(e.g., by using certificate authentication, key exchangeauthentication), and so on.

Position control data 204 may additionally be communicated, useful tomove or otherwise position components of the NDT devices 12. Indeed,certain components of the NDT devices 12 may be physically movedremotely by using, for example, a virtual joystick. Advantageously, avariety of remote operations, training, and collaboration may beenabled. For example, an expert operator may train a new borescopeoperator on the job. The new borescope operator may hold the borescope14 and observe while the expert operator controls the borescope 14 byusing the mobile device 22. The expert operator may then point out tipcontrol techniques, relate what type of observations are correlative tocorrosion, show how to make annotations, and so on. In other cases, theexpert operator may be located at a different geographic location andmay collaborate and/or train the new borescope operator by the use ofVOIP, whiteboarding, and the like, or may use the mobile device 22 toperform a full inspection remotely. In another training example, the newborescope operator may be using the mobile device 22 and/or borescope14, and receive training from remote locations, such as web-basedlocations. For example, the screen 137 of the mobile device 22 may beportioned into multiple viewing areas (e.g., “splitscreens”) so that oneviewing area shows borescope 14 images or video while a second viewingarea shows a training video, and a third area shows an online equipmentmanual procured wirelessly. Indeed, the boresecope 14 may receive data,including targeted multimedia inspection data from external sources(e.g., mobile device 22, cloud 24, computing system 29).

Additionally, fine control data 206 may be communicated. For example,“jogging” data suitable for moving the borescope's articulating section122 and/or the PTZ camera 16 at smaller increments than the positioncontrol data 204. More specifically, the fine control data 206 mayinclude a step to move (e.g., 0.5 mm, between 0.05 mm and 1 cm or more),and a number of steps to move (e.g., 1, 2, 3, 4, 5 or more).Accordingly, components of the NDT device 12 may be more preciselydisposed to better observe certain features undergoing inspection. Theposition control data 204 and fine control data 206 may be produced byvirtual controllers or physical controllers communicatively connected tothe NDT devices 12.

Images, video, text, and/or audio data 208 may be additionallycommunicated. For example, the mobile device 22, the cloud 24, and/ordevices coupled to the cloud (e.g., computing system 29) may send imagesand/or video, as well as overlay annotations useful in illustrating tothe borescope operator certain features to inspect further, along withaudio detailing explanations of how to proceed with the inspection. Incertain embodiments, the data 208 may be training data useful indetailing inspection procedures. In other embodiment, the data 208 mayinclude data transmitted from experts, detailing instructions on how tomore thoroughly inspect certain equipment. In yet another embodiment,the data 208 may include data sent through automated entities (e.g.,expert systems, fuzzy logic systems, neural network systems, statevector machines) based on received data from FIG. 6 useful in directingand/or focusing the inspection after automatically analyzing thereceived data.

Configuration data 210 may also be communicated. For example data usedto update file systems included in the NDT devices 12, to reprogram theNDT devices 12, to set parameters useful in operating the NDT devices12, and/or to reconfigure electronic components of the device 12 (e.g.,flash upgrade) may be sent to the NDT inspection devices 12 remotely.Indeed, programming and parameter-setting may be done remotely, thusproviding for techniques to more easily maintain the NDT devices up todate, and to improve device operations. It is to be understood thatdifferent NDT devices 12 may use different parameter sets. As anon-limiting example only, some parameters, e.g., used during operationsof the NDT device 12 and useful to remote control the NDT devices 12 mayinclude parameters for starting acquisition of data, stoppingacquisition of data, saving a file, naming or renaming a file, adjustinga gain, adjusting a time base, compensating for lift off—zeroing signalduring eddy current inspection, adjusting phase rotation, adjustingpersistence, balancing a probe, adjusting gate (e.g., amplitudeadjustment, position adjustment), adjusting color palette—soft gain,changing signal rectification, changing pulser filter, zooming in andout, adjusting a pulse width, adjusting a data filter (e.g., bandwidth),adjusting pulse repetition frequency, adjusting sweep angle start/stop,adjusting sweep angle increment, turning channels on/off, freezing data,clearing/erasing data, adjusting span, adjusting filters, changing spotpositions, changing display types (e.g., spot display, timebase display,waterfall display), and/or changing channel views.

In one embodiment, client-server techniques, such as virtual networkcomputing (VNC), remote desktop protocol (RDP), desktop sharing, amongothers, may be used to send configuration data 210 and receive datacorrelative with screen control of the NDT devices 12. Likewise, remotefile system control may be provided by using techniques such as securefile transfer protocol (ftp), ftp over secure shell (SSH), remote filesharing (RFS), and/or distributed file systems (e.g., using the cloud 24to store and retrieve files through the NDT devices 12). Files may beadded, renamed, deleted, and/or updated. Likewise, file folders andother file storage structures may be similarly renamed, deleted, and/orupdated.

Force feedback data 212 may additionally be communicated. For example, amore forceful push onto the mobile device's 22 touchscreen may translateinto data 212 useful in moving the borescope's articulating section 122more quickly. Likewise, a haptic controller may be coupled to thecomputing device 29 and provide the force feedback data. The more forceapplied, the faster the correlative movement of components such as thearticulating section 122 of the borescope 14. It is to be noted thatforce feedback data 212 may be provided by other devices, such as thephysical joystick 131, a virtual joystick, haptic controllers wirelesslycoupled to the NDT devices 12, including controllers coupled through thecloud 24 or mobile device 22 (e.g., when the mobile device 22 isproviding for WAP functionality). Other data 214 may include updateddigital manuals or help manuals useful in operating the NDT devices 12,manuals relating to the equipment (e.g., turbomachinery 18, aircraft104) undergoing inspection, and so on. Accordingly, the wireless conduit200 would be used to communicate and to change or otherwise modify NDTdevice 12 information, such as borescope-specific information includingbut not limited to measurement information (cursor placement,measurements, stereo matches), MDI information (current stage, assetinformation, reference material), current menu selections, tiptemperatures/pressures, tip orientation (tip map, artificial horizon),3-dimensional phase measurement (3DPM) range indication, textannotation, and so on. Software control applications may render nativegraphics with touchscreen buttons or softkey labels as described in moredetail below, and if appropriate, accept user input. Hard physicalbuttons with either fixed or dynamic functionality can also be used toaccept input. It is to be noted that the NDT device 12 may be controlledby a first entity (or more than one remote entities) at the same time asthe NDT device 12 is used by a second entity. Indeed, the controlembodiments described herein enable multiple parties to control thedevice at the same time, including multiple remote parties.

FIG. 8 is illustrative of an embodiment of a NDT ecosystem 300 useful inproviding for a collaboratory environment between, for example, betweenthe NDT device 12, the mobile device 22, the computing system 29, anasset owner 302, an inspection solution provider 304, regulatoryentities 306, other entities 308, an asset original equipmentmanufacturer (OEM) 310, asset inspection providers 312, and/orapplication developers 314. The NDT ecosystem 300, or portions of theNDT ecosystem 300, may be implemented by executable computerinstructions stored in a memory 316 and executed by a processor 318. Thememory 316 and processor 318 may be included in a system inside thecloud 24 or connected to the cloud 24, including but not limited tocomputing servers, virtual machines, load balanced computing devices,and the like.

In the depicted embodiment, the asset owner 302 may include the owner orlessee of equipment and facility assets, such as turbomachinery 18,aircraft 104, and/or facilities 20, 106. The inspection solutionprovider 304 may include a company or entity that develops software andhardware useful in performing the process 150 or components of theprocess 150, including the inspection 154. Regulatory entities 306 mayinclude state and federal agencies that regulate all or portions of theprocess 150. Other entities 308 may include entities providing cloudcomputing services 24, such as entities providing connectivity services(e.g., wired and/or wireless connectivity), backend computing services(e.g., cloud based computer processing services, grid computingservices, cluster computing services, supercomputing services, and/orcloud based storage services). The asset OEM 310 includes themanufacturer of the aforementioned equipment and facilities assets. Theasset inspection providers 312 include entities that provide, forexample, personnel and equipment used in the inspection 154.

Application developers 314 include any entity, including but not limitedto the aforementioned entities 302, 304, 306, 308, 310, 312 that maywrite digital content 320, including computer executable content 322(e.g., applications) and/or non-executable content 324 (e.g., equipmentmanuals, inspection procedures, training procedures, regulatorydocuments, regulatory procedures, and so on). The digital content may bestored in a repository (e.g., database) included in the NDT ecosystem300. The applications may include applications executable by the NDTdevice 12, the mobile device 22, the computing system 19, executable inthe cloud 24 or a combination thereof. Likewise, non-executable content324 may be viewable by using the NDT device 12, the mobile device 22,and the computing system 19. Accordingly, collaboration by using the NDTecosystem 300 may involve inception of an idea for the NDT digitalcontent 320, and the creation, distribution, purchase, management andrevenue sharing of the NDT digital content 320.

For example, the inspection solution provider 304 may create digitalcontent 320 (e.g., applications) and hardware solutions to support thedigital content 320. The applications (and other digital content 320)may be created and tested by using a digital content builder 325,described in more detail below. These applications may then be executedon the NDT devices 12, mobile device 22, and/or computing system 29 tosupport the process 150, including the planning 152, inspection 154,analysis 156, reporting 158, and/or sharing 160. It is to be noted thatthe digital content 320, including applications, may be constructed byany of the entities 302, 304, 306, 308, 310, 312, and 314, by thirdparties, and so on, and distributed, for example, by using digitalcontent stores 326. The digital content stores 326 may include publicstores 328, private stores 330, and other stores 332. The public stores328 may include stores accessible by all entities 302, 304, 306, 308,310, 312, and 314, while the private stores 330 may include stores thatare accessible only to a subset of each of the entities 302, 304, 306,308, 310, 312, and 314, of a subset of all of the entities 302, 304,306, 308, 310, 312, and 314. Other stores 332 may include stores thatcater to entities that have received governmental approval to buy andsell government-restricted items, such as export control items. Byproviding for the creation and distribution of a variety of digitalcontent 320 by entities having a variety of expertise, the NDT ecosystem300 may provide for enhanced collaboration and a more efficient process150.

Continuing with FIG. 8 , the digital content 320 may additionallyinclude certain platform capabilities, such as application programminginterfaces (APIs), interfaces to data analysis services, hardwareinterfaces, (e.g., interfaces to the NDT devices 12), and the like. Theinspection solution provider 304 may also provide techniques suitablefor upgrading platform capabilities, for example, of the devices 12, 22,24 either by using software, or by using certain hardware (e.g., WIFImodules used to retrofit previous models of the NDT devices 12), or acombination thereof. Other techniques, including automatic updating ofdigital content on NDT devices 12, the management of software andhardware assets, the more efficient purchasing and revenue sharing ofdigital content 320, and improved techniques for maintaining userprofiles, may be provided by using the techniques described herein, suchas the NDT ecosystem 300.

The application developers 314 may create the applications and otherdigital content 320 (e.g., firmware, platform APIs, platform supportsoftware) executable or displayable by the NDT devices 12 using, forexample, the digital content builder software 325. The digital contentbuilding software 325 may include language compilers, interpreters,emulators (e.g., NDT device 12 emulators), debugging features, graphicaluser interface (GUI) builders, database connectivity builders, and thelike, useful in creating the executable content 322 and thenon-executable content 324. Additionally, the digital content buildingsoftware 325 may include tie-ins to external systems 327, includingknowledge based systems (e.g., expert systems, expert reasoning systems,fuzzy logic systems, heuristic reasoning systems), which may include“canned” human expert knowledge and experience useful in developing thedigital content 320.

Once the digital content 320 has been developed, including applications,training manuals, user manuals, and other associated documents, theapplication developers may upload the digital content for distributionby the digital stores 326. In the depicted embodiment, an automatedauthentication system 329 may check for the authenticity of the digitalcontent 320 and may insure that the digital content 320 confirms to thepublishing guidelines published, for example, by the inspection solutionprovider 394. Additionally, the digital content 320 may be processed bya security/certificate system 331 suitable, for example, for creatingdigital certificates, for interacting with third party certificateauthorities, for encrypting the digital content 320, and more generally,for providing secure access to the NDT ecosystem 300.

As mentioned above, all of the entities 302, 304, 306, 308, 310, 312,and 314 may create digital content 320. For example, the asset OEM 310or other parties can publish inspection manuals or solutions through theNDT Application ecosystem 300. Accordingly, the asset owner 302 and/orasset inspection providers 312 may purchase the digital content 320created by the asset OEM 310, inspection solution provider 304,regulatory entities 306, and/or other entities 308, and “subscribe” toupdated content 320, as described in more detail below, to receiveupdated content 320. The asset inspection providers 312 may createdigital content 320, such as inspection-of-assets training content, ormay sell inspection services through the digital stores 326. Likewise,application developers 314 may sell a variety of software applicationssupporting the process 150 or portions of the process 150 and executableby the devices 12, 22, 29. All digital content 320 created by theentities 302, 304, 306, 308, 310, 312, and 314 may be managed, forexample by using a licensing/asset management system 322, to provide formore efficient updates, deployment, and the like, of the digital content320, and to manage licensing of the content 320, including digitalrights management (DRM). Other systems 336 may include systems useful insupporting cloud computing 24, such as cloud based storage systems,scalable processing systems, data analysis systems, databases, virtualmachines, load balancers, and the like.

Hardware may also be purchased by using the digital stores 326, such asNDT 12 device accessories, hardware platform upgrades for the NDTdevices 12, and the like. By providing for an NDT business platform, theNDT ecosystem 300 may enable revenue sharing between the entities 302,304, 306, 308, 310, 312, and 314. For example the application developers314, the asset OEM 310, and the inspection solution provider 304 mayenter into a revenue sharing policy. An accounting management system 334may be additionally provided, useful to manage credits, debits, and, andmore generally, accounting information related to the NDT ecosystem 300.For example, each of the entities 302, 304, 306, 308, 310, 312, and 314,and other users, may keep one or more store 326 accounts managed by thesystem 334. Sales and purchases related to each entity 302, 304, 306,308, 310, 312, and 314, and other users, may then be credited or debitedaccordingly. In a related manner, the licensing/asset management system333 may keep entity 302, 304, 306, 308, 310, 312, and 314 accountsuseful in managing the assets, such as the NDT devices 12 and digitalcontent 320 associated with the NDT devices 12. For example, oncedigital content 320 is purchased by the inspection provider 312, theinspection provider 312 can log into the licensing/asset managementsystem 333 to view software assets (e.g., digital content 320) andcorrelative hardware assets (e.g., equipment to be inspected, NDTdevices 12) listed in their account, to create links between softwareand hardware assets, update links, delete links, and so on, as describedin more detail below.

During the initiation of an inspection 154 that is using the NDT device12, the device 12 may then connect to the NDT ecosystem 300 and all theexecutable content 322 (e.g., applications) along with correspondingnon-executable content 324 (e.g., manuals, historical inspectionresults, analysis reports) may be automatically downloaded and thedevice 12 may be configured to use the downloaded content during theinspection 154. For example, the device 12 may receive or scan the tailnumber of a specific aircraft 104 and all digital content 320 related tothat model of aircraft 104, components of the aircraft 104 (e.g.,engines, airframe), historical logs of the specific tail number,analysis performed on the tail number, maintenance logs, operationallogs (e.g., describing equipment operations and time) and so on, may beautomatically downloaded onto the NDT device 12 to configure the NDTdevice 12 for inspection of the specific tail number. Indeed, equipment,including specific equipment identified by serial number, tail number,and so on, may be used to download a custom package of digital content320, including firmware, targeted to inspect the specific equipment.Accordingly, a more efficient and focused inspection may be realized.Indeed, by using the NDT ecosystem 300, a variety of processes suitableto enable, for example, more efficient purchasing, the management oflicenses, deployment of NDT devices 12, and maintenance/updating may beprovided, as described below with respect to FIG. ??.

FIG. 9 depicts an embodiment of digital content 320 that may bedistributed by using the NDT ecosystem 300. In the depicted embodiment,the licensing/asset management system 333 may support at least twocategories of distribution of the content 320, a “no copy” category 340,where copying of the digital content 320 is not allowed, and a “fullcopy” category 342 where copying of the digital content is fullyallowed. Likewise, the licensing/asset management system 333 may supportat least two categories of editing of the content 320. For example, a“limited edit” category may be supported, where editing of some of thecontent (or no editing) by non-authors is enforced. A “full edit”category 346 may be used when full editing of the content 320 bynon-authors is allowed. Accordingly, the digital content 320 may includea “3^(rd) party locked” digital content 348 where no copying and limitedediting is enforced, and an “in-house locked” digital content 350 wherefull copying but limited editing is allowed. Likewise, a “3^(rd) partyopen” digital content 352 may be provided, where full editing but nocopying is allowed, and an “in-house open” digital content 354 wherefull editing and full copying is allowed. DRM and other techniques maybe used by the licensing/asset management system 333 to enforce thecategories 340, 342, 344, and 346. The content may be distributed byusing the digital stores 326 and/or by other distribution channels inthe NDT ecosystem 300 (e.g., file transfer protocol [ftp] servers, webservers, cloud-based storage drives).

Accordingly, customers may search for online digital content, using, forexample, filtered searches, contextual searches, search-as-you-type,Boolean searches, and so on, to find the digital content 320 provided bythe digital stores 326 and/or the other distribution channels. Oncedesired content 320 is found, the users (e.g., entities 302, 304, 306,308, 310, 312, 314, and others) may pay for digital content by using thedigital stores 326, with account information managed by the accountingmanagement system 334. Multiple payment options may be supported,including credit cards, debit cards, purchase orders, coupons, banktransfers, and the like. Multiple license types may be supported,including annual licenses that expire once a year, perpetual licenses,monthly licenses, weekly licenses, single use licenses (expire after asingle use of the digital content 320 and can be renewed for anotheruse), and so on, by the licensing/asset management system 333, and DRMmay be enforced. Multiple seats of the same digital content 320 may alsobe purchased, suitable for use by more than one user and/or NDT device12, mobile device 22, and computing device 29.

The customers may then edit some of the purchased content, such asinspection procedures, or may create new content, both for distributionthrough the NDT ecosystem 300 (e.g., by using the digital stores 326) asmentioned above with respect to FIG. 9 . In certain cases, the customersmay create private stores 330 where only users vetted by the customermay buy digital content 320 (and hardware or services). In other cases,public stores 328 may be used or created, where the digital content (andhardware or services) may be sold to the public. Other stores 336 may beused to sell, for example, restricted goods and services, such as exportcontrolled goods and services.

Accounts for customer assets (e.g., software assets like the content 320and associated hardware like the NDT device 12) may be provided by usingthe licensing/asset management system 333. Multiple devices 12, 22,and/or 29 may be managed for a given single account. One-buttonsynchronization/deployment may be provided, as described in more detailbelow, suitable for synchronizing the devices 12, 22, and/or 29 with thepurchased digital content 320. Accordingly, the devices 12, 22, and/or29 may be kept up to date on NDT content 320, including contentdelivered across geographic regions and in multiple languages.

Turning now to FIG. 10 , the figure is a flowchart illustrating anembodiment of a process 400 suitable for purchasing goods and servicesby using the NDT stores 326. The process 400 may be implemented by usingcomputer executable instructions stored in the memory 316 and executedby the processor 318. In the depicted embodiment, the user (e.g., 302,304, 306, 308, 310, 312, and/or 314) may search (block 402) for NDTgoods and services (e.g., digital content 320) and be directed to aproduct detail page 403 based on the search. The search (block 402) maybe performed by using the NDT devices 12, the mobile device 22, thecomputing system 29, or a combination thereof. The user may then add aproduct to an online cart (block 406). The process 400 may thendetermine if the user is logged in (decision 408). If the user is notlogged in, the user may then log in (block 410). The user may thencreate an account (block 412). Once the user is logged in, a paymentmethod may be determined (decision 414). If the payment method is apurchase order 416, the user may then enter a purchase order (PO)information (block 418), the process 400 may then show a receipt (block420), and subsequently enable download (block 422) of digital content320 by using the digital stores 326 and add application contentinformation to a “My Apps” system (block 424), including accountinformation. License purchasing may be similarly added to a “My Wallet”system.

If the payment method is determined (decision 414) to include coupons426, the process 400 may then ask for purchase confirmation (block 428).Once confirmed, the receipt may be shown (block 420), and downloads(block 422) and/or updates to “My Apps” (block 424) may be provided. Ifthe payment method is determined (decision 414) to include a credit card429, the process 400 may determine (decision 430) if credit card 429information has been saved. If information has been saved, the process400 may then enable the verification of the information (block 432),such as address, expiration date, and the like, and may then ask forpurchase confirmation (block 434). If the card information is accepted(decision 436), the receipt may be shown (block 420), and downloads(block 422) and/or updates to “My Apps” (block 424) may be provided. Ifthe card is not accepted (decision 436), the process 400 may iterateback to decision 414 and ask for payment method.

If the card information is not saved (decision 430) the user may entercredit card information (block 438), such as billing address, names,dates, security numbers, and the like. The process 400 may then ask forpurchase confirmation (block 440). If it is determined that there is aremaining balance (decision 442), the process 400 may iterate todecision 414 and ask for a payment method. If there is no balance, theprocess 400 may shown the receipt (block 420), and downloads (block 422)and/or updates to “My Apps” (block 424) may be provided. Accordingly,various payment methods may be used to purchase goods and services,including digital content 320 in the online stores 326.

FIG. 11 is a flowchart illustrating an embodiment of a process 450suitable for using the licensing/asset management system 333 to assignand/or remove licenses. The process 450 may be implemented by usingcomputer executable instructions stored in the memory 316 and executedby the processor 318. In the depicted embodiment, the user may log in toa “My Wallet” system 452. The system 452 may include purchased licenses,such as licenses to use certain digital content 320 in the NDT devices12, the mobile device 22, and/or the computing system 29. The user(e.g., 302, 304, 306, 308, 310, 312, and 314) may use the system 452 toassign a license (block 454), for example, to a desired NDT device 12,mobile device 22, and/or computing system 29. However, if it isdetermined (decision 456) that no licenses are available, the process450 may issue an error message (block 458). If licenses are available(decision 456) but it is determined that there are duplicate licenses(decision 460), the process 450 may issue an error message (block 458).

If it is determined (decision 460) that no duplicates exists, theprocess 450 may update (block 462) a device 12, 22, and/or 29 object anddecrement a count of user licenses. The object may be a virtual oronline representation of a physical device 12, 22, and/or 29 which maybe used to synchronize content 320 with the corresponding device 12, 22,and/or 29. The process 450 may then issue a confirmation (block 464) ofthe allocation of the license, for example, via email.

To remove a license (block 466) that has been allocated to a physicaldevice 12, 22, and/or 29, the process 450 may select the device (block468), for example, from a list of devices kept by the “My Wallet” system452. The process 450 may then notify (block 470) the user that theupdate (e.g., removal of the license) may occur in the nextsynchronization, described in more detail in FIG. 12 . There may be adelay (block 472) while the synchronization (block 473) occurs. Aftersynchronization (block 473), the process 450 may update (block 474) theobject associated with the physical device 12, 22, and/or 29, incrementa license count, and may then issue a confirmation (block 476) of theremoval of the license, for example, via email. Accordingly, licensesmay be assigned or de-assigned to any of the devices 12, 22, and/or 29.

FIG. 12 is a flowchart depicting an embodiment of a process 480 suitablefor synchronizing the devices 12, 22, and/or 29 with, for example,purchased and licensed digital content 320. The process 480 may beimplemented by using computer executable instructions stored in thememory 316 and executed by the processor 318. In the depictedembodiment, the user may interface with a device menu 482 to select a“synchronize” activity (block 484). The process 480 may then determine(block 486) if the device 12, 22, and/or 29 is found, for example, in adevice database described in more detail with respect to FIG. 13 below.If it is determined (decision 486) that the device is not in the devicedatabase, the process 480 may issue an error message (block 488) andexit. If it is determined (decision 486) that the device is in thedevice database, the process 480 may then determine (block 490) if thereis enough memory space in the device 12, 22, and/or 29 to downloadcontent 320 purchase and licensed to the device 12, 22, and/or 29. If itis determined that there is not enough space (decision 490), the process480 may then enable the selection (block 492) of a subset of digitalcontent 320, such as executable 322 applications that may fit in thememory.

If it is determined that there is enough space (decision 490), theprocess 480 may then incrementally synchronize (block 494) the selectedcontent 320, which may include firmware, into the device's memory. Forexample, the memory may be incrementally “flashed” to add the content320. Once the content 320 is added, the process 480 may then display(block 496) a status message indicative of the synchronization of thecontent 320. By enabling a more efficient NDT-based synchronizationprocess 480, the techniques described herein may provide for a varietyof content 320 that is more easily distributed across entities andgeographies.

Turning now to FIG. 13 , the figure is a flowchart illustrating anembodiment of a process 500 suitable for adding a device, such as theNDT devices 12, mobile device 22, and or computing system 29 to the NDTecosystem 300. For example, users (e.g., 302, 304, 306, 308, 310, 312,and 314) may log into the licensing/asset management system 333 and usea “My Instruments” system 502 to add a device (block 504). In thedepicted embodiment, the device may be added by activating or clicking(block 506) a device assignment on the device 12, 22, and/or 29 itself,which may then communicate with the system 502. An activation passkeymay be received (block 508) either on the device 12, 22, and/or 29 or inanother device, for example, sent by the system 502. The user may thenenter (block 510) a serial number and the activation key, or otheridentifying information used in identifying the device to be added. Theinformation may be checked (decision 512) for validity, and if notsuccessful, the process 500 may issue an error message (block 514). Ifit is determined (decision 512) that the information is valid, theprocess 500 may add the device to the device database, for examplelinked to the user's account, and complete execution (block 516).Accordingly, the process 500 may more efficiently commission orotherwise add devices 12, 22, and/or 29 for participation in theecosystem 300.

Technical effects of the invention include providing for an NDTecosystem useful in increasing collaboration between parties, includingbut not limited to asset owners, inspection solution providers,regulatory entities, asset OEMs, asset inspection providers, andapplication developers.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated methods. The patentable scope ofthe invention is defined by the claims, and may include other examplesthat occur to those skilled in the art. Such other examples are intendedto be within the scope of the claims if they have structural elementsthat do not differ from the literal language of the claims, or if theyinclude equivalent structural elements with insubstantial differencesfrom the literal languages of the claims.

The invention claimed is:
 1. A non-transitory computer readable mediumcomprising executable instructions which, when executed by a processorof a remote device, cause the processor to: communicatively couple to anon-destructive testing (NDT) ecosystem and the NDT device, the NDTecosystem including a processor executing computer instructions storedin memory to implement, the NDT ecosystem comprising: a repository ofdigital content created by a plurality of entities, wherein the digitalcontent comprises executable content that, when executed by the remotedevice, causes the NDT device to generate overlay-enhanced views using asynchronization signal; and a public store created by a machinery assetinspection provider included in the plurality of entities and configuredto provide the digital content to a customer, wherein the digitalcontent includes training content associated with inspecting themachinery asset acquire the digital content from the public store andtransmit the digital content to the NDT device; remotely execute thedigital content to control at least one operation of the NDT deviceduring an inspection of a machinery asset, the at least one operationbeing independent of a visual modality.
 2. The non-transitory computerreadable medium of claim 1, wherein the machinery asset includes aturbomachinery, a compressor, a pump, a turbo expander, a wind turbine,a hydroturbine, and components of the machinery asset.
 3. Thenon-transitory computer readable medium of claim 2, wherein the NDTdevice includes a fiberscope, a robotic pipe inspection device, arobotic crawler, a borescope, an ultrasonic inspection device, an X-rayinspection device, an eddy current inspection device, or a combinationthereof.
 4. The non-transitory computer readable medium of claim 1,wherein the digital content further comprises non-executable digitalcontent.
 5. The non-transitory computer readable medium of claim 4,wherein the non-executable digital content comprises an NDT devicemanual, a regulatory document or a combination thereof.
 6. Thenon-transitory computer readable medium of claim 1, wherein the NDTecosystem further comprises a private store configured to sell thedigital content to the customer, wherein the customer is vetted, and anexport controlled store configured to sell export controlled digitalcontent to an additional customer, wherein the additional customer isvetted by a government.
 7. The non-transitory computer readable mediumof claim 1, comprising executable instructions causing the processor todownload the digital content into a memory of the NDT device based on anidentifier identifying the machinery asset.
 8. The non-transitorycomputer readable medium of claim 7, wherein the instructions, whenexecuted cause a performance of operations including: analyzinginspection data generated by the NDT device during the inspection of themachinery asset; recording the inspection data in a memory of a mobiledevice; and guiding the inspection of the machinery asset usingmenu-driven inspection techniques.
 9. The non-transitory computerreadable medium of claim 8, wherein analyzing the inspection datafurther includes: determining one or more of a part replacementschedule, a maintenance schedule, a machinery utilization schedule, apersonnel usage schedule, and a new inspection schedule; and generatingone or more reports associated with the analyzed inspection data. 10.The non-transitory computer readable medium of claim 8, wherein theguiding the inspection of the machinery asset further includestransmitting audio data from a mobile device to the NDT device, theaudio data including instructions informing an operator of the NDTdevice of inspection procedures.
 11. The non-transitory computerreadable medium of claim 1, wherein the plurality of entities comprisean asset owner, an inspection solution provider, a regulatory entity, anasset OEM, an application developer, or a combination thereof.
 12. Asystem comprising: a non-destructive testing device (NDT); an NDTecosystem comprising a repository of digital content and a public storeconfigured to provide the digital content to a customer; a mobile devicecomprised of a processor, wherein the processor is configured todownload the digital content from the NDT ecosystem, created by aplurality of entities, the digital content comprising an executablecontent that, when executed by the processor, causes the NDT device togenerate overlay-enhanced views using a synchronization signal, whereinthe mobile device is communicatively coupled to the NDT device and theNDT ecosystem, the mobile device is configured to: acquire the digitalcontent from the public store and transmit the digital content to theNDT device; and remotely execute the digital content to control at leastone operation of the NDT device during an inspection of a machineryasset, the at least one operation being independent of a visualmodality, wherein the NDT device includes at least one sensor configuredto acquire sensor data.
 13. The system of claim 12, wherein the NDTdevice is configured to transmit an identifier to the mobile device. 14.The system of claim 12, wherein the NDT device is further configured totransmit force feedback data associated with the inspection of themachinery asset to the mobile device.
 15. The system of claim 14,wherein the mobile device includes a plurality of fluid-filledmicrochannels which may alter fluid pressure and/or redirect fluid basedon the transmitted force feedback data.
 16. The system of claim 12,wherein executing the executable content further causes the processor toperform operations comprising: implementing a communication protocolbetween the NDT device and the mobile device, the communication protocolenabling control data communication between the NDT device and themobile device; analyzing inspection data generated by the NDT deviceduring the inspection of the machinery asset; and recording theinspection data in a memory of the mobile device; guiding the inspectionof the machinery asset using menu-driven inspection techniques.
 17. Thesystem of claim 16, wherein analyzing the inspection data furtherincludes: determining one or more of a part replacement schedule, amaintenance schedule, a machinery utilization schedule, a personnelusage schedule, and a new inspection schedule; and generating one ormore reports associated with the analyzed inspection data.
 18. Thesystem of claim 16, wherein the guiding the inspection of the machineryasset further includes transmitting audio data from the mobile device tothe NDT device, the audio data including instructions informing anoperator of the NDT device of inspection procedures.